Debugger and application control
Either the Debugger or the executing application has control during a debugging session. The Debugger has control when no application is running or the running application is interrupted, for example, at a breakpoint. When the Debugger has control, it can send commands to the client process for execution. The application has control whenever it is executing 4GL code, for example, in response to a Debugger control flow command such as Debug
Continue. When the application has control, it interacts with the user and database as if the Debugger were not running.
The following sections detail the Debugger and application interaction:
Application interaction during Debugger control
When the Debugger has control, the application is blocked. At this point, the client application is waiting to execute a line of code. The application continues to wait until you invoke a Debugger control flow command such as Debug Step Into, Debug Step Over, Debug Step Out, or Debug Continue.
Debugger interaction during application control
When the application has control (is executing), you cannot invoke commands in the Debugger window until the Debugger receives control (for example, when the application reaches a breakpoint). You can force the Debugger to take control during procedure execution by using Debug Interrupt.